[3.12] gh-157190: Fix tarfile data/tar filter bypass via hard link to a symlink (GH-157191) (GH-157192) - #157454

… MCP lock

Touching api/ woke the API container gate, and Grype (not Trivy)
blocks on CVE-2026-82049, HIGH, in the CPython 3.12.13 interpreter of
the base image. The SDK image shares the base and fails the same way.
It is pre-existing on master, not caused by the anyio bump.

There is no fixed CPython release on any branch: the fix is merged on
main and 3.13 only, the 3.12 backport is still open:
python/cpython#157454
Grype records 3.14.0b1 as the fix, so only-fixed does not drop it,
and python:3.12.14-slim-trixie reports it too, so a base image bump
does not help. Upstream issue:
python/cpython#157190

Exposure: the CVE is a tarfile extraction-filter bypass. Prowler
never extracts tar archives to disk; the only first-party tarfile
use (ECR image inspection) reads members in memory with
extractfile().

Changing .grype.yaml wakes the MCP and UI container gates too, and
the MCP lock still carried anyio 4.13.0, so it is bumped here to
4.14.2 (lock only, anyio is transitive there). The lock change is
byte-identical to dependabot's #12844, which this supersedes.

Verified with Grype 0.116.1 (the CI version), --only-fixed --by-cve,
against python:3.12.13-slim-trixie: master's .grype.yaml reports
CVE-2026-82049 on python, the updated one reports no High/Critical
python findings.